home *** CD-ROM | disk | FTP | other *** search
- COMPILING THE AUDIO EXAMPLES
- ============================
-
- I tried all three versions of C compilers that I have.
- The following sequence of commands produced the object
- files you have on this disk.
-
- The object files in the directory EXECUTABLE.FILES
-
- They are labeled AmigaC.exe
- ManxC.exe
- LatticeC.exe
-
- ---------------------------------------------------------------------
- NOTE: These instructions are for RELEASE.1 Source code.
-
- I have since combined globals.c and audiotools.h into the tools source
- code and therefore you will not necessarily find those files in later
- releases.
- ---------------------------------------------------------------------
-
-
-
- Common to ALL sequences: (Note: I use a two 3.5 inch floppy system)
- -------------------------
- copy audiotools.h to ram:
- copy globals.c to ram:
- copy audiotools.c to ram:
-
-
- --------------------------------------------------------------------
- If you are using Amiga C in drive df1:
- (Lattice C, 3.03)
-
- cd df1:examples
-
- execute makesimple ram:audiotools
-
- rename ram:audiotools to ram:audio.AmiC.exe
-
- ---------------------------------------------------------------------
- If you are using Manx C, V3.4a (with patch 1.3), Disk 1 in drive df0:
-
- cc +L ram:audiotools.c
-
- ln +A ram:audiotools.o c32.lib
-
- rename ram:audiotools to ram:audio.ManxC.exe
-
- ---------------------------------------------------------------------
- If you are using Lattice C 3.10 Disk #1 in drive df0:
- and Disk #2 in drive df1:
-
- cd ram:
-
- lc1 audiotools
- lc2 audiotools
-
- blink from LIB:c.o+audiotools.o to audiotools LIB LIB:lc.lib+LIB:amiga.lib
-
- rename ram:audiotools to ram:audio.LatC.exe
-
-
- -----------------------------------------------------------------
- My apologies to C-purists. The listings in the magazine had
- to be crammed down so that they'd fit a 56-column wide line.
- If I had known that in advance of submitting them, I would
- have watched my line lengths a bit better.
-
- Also, there are a few routines here for which there is a
- "return(0)" stuffed in at the end, for no apparent reason.
- These lines are totally extraneous in most cases and were
- simply installed to keep one of the compilers from
- issuing any warnings about return value mismatches.
-
- This same code compiles with no warnings or errors on
- any one of the above named compilers.
-
- Please note that I have released these routines into the public
- domain, essentially with no promise of support. However, I
- am interested in monitoring what the routines finally become.
- I plan to release upgrades on an as-available basis (described
- in UPDATE.POLICY), but basically you are on your own.
-
- I WOULD like to hear about bugs you may uncover. I do believe,
- however, that I have provided for much of the error handling
- you might need. Because it is public domain, and no support
- or guarantees are provided, if you do find bugs, I cannot
- promise to be able to fix them, but I'll at least acknowledge
- their receipt if you do report them. If there is a fix, I'll
- tell you about it.
-
-
- Good luck.
-
-
- Rob Peck
-